Thank you for using the OVH Load Balancer.

In order to provide you with the best service quality, we reworked our Load Balancer offers during 2017.
The service migration to our new high availability architecture occurred on January 25th 2017.
The API and customer panel migration phase will take place this month.

Starting on December 11th 2017 at 00h00 UTC+1, all Load Balancers will be automatically migrated.
This is a technical operation. It has not impact on the service billing.
No action is required from your part.

Warning: if you use the old API, you must update your scripts.
You can find the API changelog, as well as the related documentation, at the end of this mail.

New customer panel: www.ovh.com/manager/cloud/login.html
Old API, deprecated starting on December 11th: eu.api.ovh.com/console/#/ip/loadBalancing
New API: eu.api.ovh.com/console/#/ipLoadbalancing

Please note your Load Balancer will keep the same level of functionality as its current offer.
We would also like to inform you about our new commercial offers: www.ovh.ie/solutions/load-balancer/
These come with new feature and guarantee of service (SLA).
These offers will be available to you on December 11th 2017, and can be apply using the following API call: eu.api.ovh.com/console/#/ip/loadBalancing/{serviceName}/switchToIplbNextGenerationApi#POST

— API CHANGELOG
API migration brings the following changes:
— each port redirection becomes now a frontend (source port) and a farm (destination port):
— the frontend is configured as TCP mode by default. It is configured in HTTP mode if:
— the source port is 80,
— the source port is 443, and the «SSL Certificate» option is activated,
— the farm is configured according to the session management,
— the backends are now servers, linked to a farm,
— the SSL certificate option is available in the panel of the same name.
— WORK TASK
For more information about the migration operations, you may consult the following «work task» (in French):
travaux.ovh.net/?do=details&id=28820
— DOCUMENTATION

For more information about your Load Balancer, you can refer to the documentation (currently in French, an english translation is ongoing):
docs.ovh.com/fr/fr/cloud/iplb/

We’re excited to announce the launch of our latest product: Load Balancers. Fully managed by DigitalOcean, create highly available setups and distribute traffic seamlessly throughout your infrastructure with just a few clicks or via the API—no ops needed.

Load Balancers can handle TCP, HTTP, and HTTPS workloads, and manage your SSL certificates. You can add Droplets to Load Balancers individually or collectively by choosing Droplet tags.

Load Balancers cost $20 per month with no additional bandwidth charges, and are available in all datacenter regions.

To learn more about what you can do with Load Balancers and how to use them, be sure to read the announcement blog post. Or click below to start incorporating Load Balancers into your infrastructure!
cloud.digitalocean.com/networking/load_balancers

travaux.ovh.net/?do=details&id=20082

Nous commençons par migrer les IP LoadBalancing de Roubaix, qui sont présent sur une seule zone.

Planning prévisionnel de migration:

• RBX: 01/09/2016 10H, 472 IP LoadBalancing
• GRA: 01/09/2016 14H 331 IP LoadBalancing
• SBG: 01/09/2016 16H, 278 IP LoadBalancing
• IPLB Anycast: 02/09/2016 10H, 227 IP LoadBalancing

Google Cloud SSL proxy terminates user SSL (TLS) connections at the global load balancing layer, then balances the connections across your instances via SSL or TCP. Cloud SSL proxy is intended for non-HTTP(S) traffic. For HTTP(S) traffic, HTTP(S) load balancing is recommended instead.
cloud.google.com/compute/docs/load-balancing/tcp-ssl/

iplbtesting.ovh/